The Trump administration is pushing an initiative for millions of Americans to upload personal health data and medical records on new apps and systems run by private tech companies, promising easier to access health records and wellness monitoring. Donald Trump is expected to deliver remarks on the initiative on Wednesday afternoon in the East Room. The event is expected to involve leaders from more than 60 companies, including major tech companies such as Google and Amazon, as well as prominent hospital systems like the Cleveland clinic. The new system will focus on diabetes and weight management, conversational artificial intelligence that helps patients, and digital tools such as QR codes and apps that register patients for check-ins or track medications. The initiative, spearheaded by an administration that has already freely shared highly personal data about Americans in ways that have tested legal bounds, could put patients' desires for more convenience at their doctor's office on a collision course with their expectations that their medical information be kept private.

A widely used Agile practice for requirements is to produce a set of user stories (also called ``agile product backlog''), which roughly includes a list of pairs (role, feature), where the role handles the feature for a certain purpose. In the context of Software Product Lines, the requirements for a family of similar systems is thus a family of user-story sets, one per system, leading to a 3-dimensional dataset composed of sets of triples (system, role, feature). In this paper, we combine Triadic Concept Analysis (TCA) and Large Language Model (LLM) prompting to suggest the user-story set required to develop a new system relying on the variability logic of an existing system family. This process consists in 1) computing 3-dimensional variability expressed as a set of TCA implications, 2) providing the designer with intelligible design options, 3) capturing the designer's selection of options, 4) proposing a first user-story set corresponding to this selection, 5) consolidating its validity according to the implications identified in step 1, while completing it if necessary, and 6) leveraging LLM to have a more comprehensive website. This process is evaluated with a dataset comprising the user-story sets of 67 similar-purpose websites.

Time Warp: The Gap Between Developers' Ideal vs Actual Workweeks in an AI-Driven Era Sukrit Kumar, Drishti Goel, Thomas Zimmermann, Brian Houck, B. Ashok, Chetan Bansal Georgia Institute of T echnology, Microsoft, Microsoft Research, University of California, Irvine Abstract --Software developers balance a variety of different tasks in a workweek, yet the allocation of time often differs from what they consider ideal. Identifying and addressing these deviations is crucial for organizations aiming to enhance the productivity and well-being of the developers. In this paper, we present the findings from a survey of 484 software developers at Microsoft, which aims to identify the key differences between how developers would like to allocate their time during an ideal workweek versus their actual workweek. Our analysis reveals significant deviations between a developer's ideal workweek and their actual workweek, with a clear correlation: as the gap between these two workweeks widens, we observe a decline in both productivity and satisfaction. By examining these deviations in specific activities, we assess their direct impact on the developers' satisfaction and productivity. Additionally, given the growing adoption of AI tools in software engineering, both in the industry and academia, we identify specific tasks and areas that could be strong candidates for automation. In this paper, we make three key contributions: 1) We quantify the impact of workweek deviations on developer productivity and satisfaction 2) We identify individual tasks that disproportionately affect satisfaction and productivity 3) We provide actual data-driven insights to guide future AI automation efforts in software engineering, aligning them with the developers' requirements and ideal workflows for maximizing their productivity and satisfaction. I NTRODUCTION In software engineering, the productivity and satisfaction of developers are pivotal factors that influence both individual performance, customer experience and ultimately, organizational success [1], [2]. The day-to-day activities which define a developer's workweek encompass a broad spectrum of tasks; from coding and designing new systems, to preparing documents, attending meetings, on-boarding new employees, adhering to security and compliance tasks, etc [3]. Each of these tasks is integral to the software development life cycle. Ideally, developers would prefer to allocate their time across these tasks in a way that optimizes both productivity and satisfaction-- this can be referred to as their'ideal workweek'. However, in practice, their'actual workweek', can vary significantly from their'ideal' due to fluctuating workloads, shifting organizational priorities, dependencies on other teams, technical challenges, the influence of the work environment, etc [4], [5], [6].

Alphabet-owned Waymo unveiled its sixth-generation Driver system on Monday with a more efficient sensor setup. Despite having a reduced camera and LiDAR sensor count from the current platform, the self-driving ride's new setup allegedly maintains safety levels. CNBC reports that the new system is built into Geely Zeekr electric vehicles. Waymo first said it would work with the Chinese EV maker in late 2021. The new platform's rides are boxier than the current-gen lineup, built on Jaguar I-PACE SUVs.

For decades, real estate commissions have been somewhat standardized, with most home sellers paying 5% to 6% commission to cover both the listing agent and the buyer's agent. A landmark agreement from the National Assn. of Realtors paved the way for a new set of rules that will likely shake up the entire industry, affecting sellers, buyers and the agents tasked with pushing deals across the finish line. The most pivotal rule change pertains to how buyers' agents are paid. Traditionally, home sellers have paid for the commission of both their agent and the buyer's agent, which critics argue stifled competition and drove up home prices. The new rule prohibits most listings from saying how much buyers' agents are paid, removing the assumption that sellers are on the hook for paying both agents.

It's understandable if you've tuned out news from the summit. The quibbles over wording--"urges" vs. "notes" vs. "emphasizes"--can all start to sound like noise. But these talks are the biggest climate event of the year, and there are some details that are worth paying attention to, not least the high-profile fight about those two words: fossil fuels. As negotiators start their treks home, let's sort through what happened at COP28 and why all these political fights matter for climate action. This story is from The Spark, our weekly newsletter giving you the inside track on all things energy and climate-related.

While other types of AI, such as large language models, are trained on huge repositories of data scraped from the internet, the same can't be done with robots, because the data needs to be physically collected. This makes it a lot harder to build and scale training databases. Similarly, while it's relatively easy to train robots to execute tasks inside a laboratory, these conditions don't necessarily translate to the messy unpredictability of a real home. To combat these problems, the team came up with a simple, easily replicable way to collect the data needed to train Dobb-E--using an iPhone attached to a reacher-grabber stick, the kind typically used to pick up trash. Then they set the iPhone to record videos of what was happening.

Sitting in a purpose-built hut in the grounds of the historic Bletchley Park country estate, British officials believed they had pulled off a diplomatic coup. On stage in front of them was the UK's technology secretary, Michelle Donelan, and behind her were high-level representatives from the US and China, together for the first time to discuss the international regulation of artificial intelligence. Even better, both countries were among 28 signatories to the "Bletchley declaration", an agreement to work together on safety standards that may prevent AI systems turning on humanity. Rishi Sunak said on Thursday: "Some said we shouldn't even invite China; others said that we could never get an agreement with them. A serious strategy for AI safety has to begin with engaging all the world's leading AI powers, and all of them have signed the Bletchley Park communique."

Overview This document describes a pragmatic approach on how to migrate enterprise computer systems to new systems that could evolve forever, address the whole organisations and that are integrated. Governance aspects are as important, if not more, than purely technical IT aspects: human resources, supply chains, call for tenders, and similar. Migration implies not starting from a green field. Style of this document {Principle} Lie if it helps and restate the obvious. Enterprise IT architecture is a complex field. Efforts have been made to make this document accessible to the widest possible public, including non-IT people. To make concepts more accessible, they might be introduced informally without being technically strict (lie) and sprinkled with bits of tutorials (restate). For the gory details follow the references. It could be anything: from one integrated system to many disconnected systems, from properly developed systems to spreadsheets, from internal developed code to external libraries, etc. The first priority is to ensure the functioning of the current system, imperfect as it might be. Avoid the syndrome of not maintaining the current system because it is a waste of money. It is an error to channel most of the IT resources into the new wonderful system on the way. The first step is to prepare emergency manuals for the current system. The guiding scenario for preparing these manuals is that present IT staff operating/maintaining the current system disappear from one day to the next; unpolished manuals would do. New IT replacement staff without any previous knowledge should have a sporting chance of operating/maintaining the current system with the help of emergency manuals which must be printed and stored in a place easy to find.

While advances in wearable robotics have helped restore mobility for people with lower limb impairments, current control methods for exoskeletons are limited in their ability to provide natural and intuitive movements for users. This can compromise balance and contribute to user fatigue and discomfort. Few studies have focused on the development of robust controllers that can optimize the user's experience in terms of safety and independence. Existing exoskeletons for lower limb rehabilitation employ a variety of technologies to help the user maintain balance, including special crutches and sensors, according to co-author Ghaith Androwis, PhD, senior research scientist in the Center for Mobility and Rehabilitation Engineering Research at Kessler Foundation and director of the Center's Rehabilitation Robotics and Research Laboratory. Exoskeletons that operate without such helpers allow more independent walking, but at the cost of added weight and slow walking speed.